This website uses cookies to ensure you get the best experience.
Learn more.
A team wants one codebase deployed to dev and prod with different catalog names. Which approach fits?
Published
- Maintain unrelated source repositories for every task run
- Copy one production access token into public source
- Manually edit production notebooks after every deployment
- Bundle targets with environment-specific configuration
Comments — 0
Sign in to comment