Unifying the Dockerfile folder structure among IaC clouds #481
Unanswered
frozentank
asked this question in
Ideas
Replies: 1 comment 2 replies
-
Hey @frozentank, thanks for the suggestion! Like you pointed out in your last paragraph, I'd be worried about breaking current users. I've been trying to think of ways that we could implement this without any disruption. My current thought is to use Docker build For example:
What are your thoughts on that? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm suggesting unifying the folder structure of the different cloud providers' (Azure, GCP, AWS) so that instead of the entrypoint being
/viya4-iac-azure/docker-entrypoint.sh
it would be something like/viya4-iac/docker-entrypoint.sh
. This helps in a few different ways, but the concern is a situation where running the container doesn't honor the entrypoint setting. This is a problem with that particular container platform (Github Actions Jobs in Containers) but the directory structure of the repositories compound the problem. I think it could be fairly straightforward change to the different code bases. I have an alternate Dockerfile for each repository for building the container but I'd prefer to use the OOB experience as much as possible. Especially since CLI tools and Terraform version bumps mean I have to maintain each Dockerfile in sync.The only concern I have with making that kind of change would be breaking any current pipelines. Technically, the current documentation is not referencing this directory structure and only the scenario I have would be impacted.
Beta Was this translation helpful? Give feedback.
All reactions