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

User guide for EnvironmentConfig #305

Closed
Tracked by #3770
jbw976 opened this issue Jan 31, 2023 · 1 comment · Fixed by #475
Closed
Tracked by #3770

User guide for EnvironmentConfig #305

jbw976 opened this issue Jan 31, 2023 · 1 comment · Fixed by #475
Labels
concepts/composition content request Issues requesting new content

Comments

@jbw976
Copy link
Member

jbw976 commented Jan 31, 2023

The ability to use configuration values from the environment is a great new feature in v1.11: crossplane/crossplane#2099.

We have some guidance on how to use them from a composition patching perspective, e.g. *Environment* in https://docs.crossplane.io/master/reference/composition/#patch-types, but it would also be helpful to have a complete end to end user guide for how to create and use EnvironmentConfig.

There was a small yaml only (no written prose or context) end to end example in the old docs snippets (see links below), but those are being cleaned up and removed. We could use those as a starting point to author a complete end to end guide on how to use EnvironmentConfig.

@djeremiah
Copy link

Existing patch docs have moved to https://docs.crossplane.io/master/concepts/composition/#patch-types

plumbis added a commit to plumbis/crossplane-docs that referenced this issue Jul 20, 2023
Signed-off-by: Pete Lumbis <pete@upbound.io>
plumbis added a commit to plumbis/crossplane-docs that referenced this issue Jul 26, 2023
Signed-off-by: Pete Lumbis <pete@upbound.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
concepts/composition content request Issues requesting new content
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants