hack,README: add quickstart-container script#20
Conversation
81557b9 to
39ae204
Compare
baeb829 to
c55916a
Compare
05f7689 to
63b5b51
Compare
63b5b51 to
327686b
Compare
b8a5a67 to
a1a38f6
Compare
5731aa5 to
1c830de
Compare
|
@crawford PTAL |
crawford
left a comment
There was a problem hiding this comment.
Who is the intended consumer of this script?
There was a problem hiding this comment.
I don't want to point people at a personal repo.
There was a problem hiding this comment.
Me neither :-) We should have an alternative for it
There was a problem hiding this comment.
I was able to set up the test repositories under the redhat organization 🙌
I see it as a example towards we can point for a hands-on demonstration of how a cincinnati stack is set up. It's also useful for quick integration tests. |
1dedea8 to
58d950b
Compare
|
@lucab what's your opinion on this? Do you see this being helpful? |
|
/refresh |
58d950b to
6b600ce
Compare
|
/cc @lucab |
|
@steveej sorry, I missed your earlier ping on this. For demo purpose, I think it makes sense to keep this at the documentation level. It is more helpful for people to see a quick example than having to dig through the variables in a bash script. My preference would be for something short and clean like https://github.com/coreos/matchbox/blob/master/Documentation/deployment.md#docker. |
I don't think it's a good comparison as that example has less complexity since it doesn't build the container first and also just instructs to run a single service. In comparison, the script I'm proposing here builds the container image, runs two services in containers and then uses curl to access the service stack. In short, this is a full life-cycle demo. I'd prefer to have this script in the repository, even without a reference from the README. How about that? |
I am not in strong opposition here, so let's go for that. Please keep the other change in README (variables for test repo), as I think it's valuable there. |
This script locally builds a container image containing the graph-builder and the policy-engine. It then runs both components in separate containers and tests the policy-engine endpoint.
The quickstart-container script enables to quickly set up and query a containerized Cincinnati stack.
6b600ce to
82e1ae5
Compare
ACK and done. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lucab, riuvshin, steveeJ The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@riuvshin PTAL