Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E2E Workflow Scripts: Use cyberark/demo-app directly from DockerHub instead of building a custom image #318

Closed
imheresamir opened this issue Jun 1, 2021 · 1 comment · Fixed by #369

Comments

@imheresamir
Copy link
Contributor

Describe the solution you would like

E2E workflow scripts should not need to build a custom cyberark/demo-app PetStore sample app to include the summon binaries. See the linked issue below in which summon was added to the demo-app. This is the tracking issue for removing the custom image building and just using the cyberark/demo-app image from DockerHub after it has been updated.

Additional context

I think we should rip all this out in favour of having summon in the demo app (see conjurdemos/pet-store-demo#35).

Originally posted by @doodlesbykumbi in #307 (comment)

@imheresamir imheresamir changed the title Use cyberark/demo-app directly from DockerHub instead of building a custom image in E2E workflow scripts E2E Workflow Scripts: Use cyberark/demo-app directly from DockerHub instead of building a custom image Jun 1, 2021
@jtuttle
Copy link
Member

jtuttle commented Aug 2, 2021

The demo-app image has not been pushed to DockerHub for a year and a half, we may need to do a tagged release to get a newer version pushed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants