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

Core Practice Content: Environment Control #279

Closed
bjennings-rise8 opened this issue Jul 17, 2024 · 7 comments
Closed

Core Practice Content: Environment Control #279

bjennings-rise8 opened this issue Jul 17, 2024 · 7 comments
Assignees
Labels
Engineering Best suited for engineers to create content

Comments

@bjennings-rise8
Copy link
Contributor

bjennings-rise8 commented Jul 17, 2024

Be sure to cover topics of:

  • Containerization
  • Environment parity
  • Infrastructure as Code
  • Configuration in the Environment

Acceptance Criteria:
Explain what the core practice is
Explain why its important
Explain it in a way that every Riser can understand it
Have a google doc that is reviewed & ready to publish
Bonus: Publish it yourself on the delivery site.

Template

Resources:

@bjennings-rise8
Copy link
Contributor Author

Schuyler offered to pick this one up!

@bjennings-rise8
Copy link
Contributor Author

Renamed "Feature Flagging" to "Configuration in the Environment" as a more general practice

@bjennings-rise8 bjennings-rise8 changed the title Environment Controls Environment Control Aug 7, 2024
@derekadombek
Copy link

derekadombek commented Aug 15, 2024

Renamed "Feature Flagging" to "Configuration in the Environment" as a more general practice

I was actually kind of wondering what we meant by "Configuration in the Environment".. Because that could mean a variety of things around deploying software, for example you could have app dependencies and networking configs, that could be completely separate from feature flags. Feature Flags are a way to turn on or off(boolean) a single component after the app is already deployed in prod or any environment to help prevent the amount of bugs to the user while testing in prod. So I am def a fan of naming this back to Feature Fags or unless we don't want it to actually be about Feature Flags.

@bjennings-rise8
Copy link
Contributor Author

I can't remember who exactly suggested including that but my assumption of what they meant was a practice of configuring things at the environment level (eg, I set an environment variable or some configuration to my database URL in the environment rather than in application code) leading to greater security and separation of concerns around what the environment controls vs what the application code has. App code reads from the environment to connect to things like services, bring in authentication keys, (possibly use feature flags) etc

Is some of that spelled out in some of the 12-factor principles? Been a min since I was an engineer but I think there may be some good stuff in the 12 factor principles we can pull from

@nsharpe-rise8 nsharpe-rise8 changed the title Environment Control Environment Control - test Aug 28, 2024
@nsharpe-rise8 nsharpe-rise8 changed the title Environment Control - test Environment Control Aug 28, 2024
@bjennings-rise8 bjennings-rise8 changed the title Environment Control Core Practice Content: Environment Control Sep 5, 2024
@bjennings-rise8 bjennings-rise8 added Engineering Best suited for engineers to create content and removed High Priority labels Sep 5, 2024
@nsharpe-rise8 nsharpe-rise8 self-assigned this Sep 14, 2024
@SagarAkre
Copy link
Collaborator

@nsharpe-rise8 do you have the link to the google doc for this?

@nsharpe-rise8
Copy link

@SagarAkre https://docs.google.com/document/d/1t3V3YS_dGHrvw1HQrKXf444z7vwrUY0_t4Y9B6NVgT4/edit?usp=drive_link

@SagarAkre
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Engineering Best suited for engineers to create content
Projects
None yet
Development

No branches or pull requests

4 participants