devops-center-feedback
devops-center-feedback copied to clipboard
forcedotcom
Populate main branch with Org Metadata
Is your feature request related to a problem? Please describe. I think could be great to populate the main branch with existing metadata in order to see actual differences between the Development Org and the next stage branch/org
Describe the solution you'd like Once we have set up the Release Org, having the environments configured At the Environments screen We can have an option to populate the branch with the Org Metadata The Metadata populated should be all Supported Metadata by DevOps Center
Additional context
Hi! The UX designer for DevOps Center here.
We have talked about this internally quite a bit, and even described it as "the big red button" just like you've drawn it!
To clarify, I think what you are asking for is an easy way to populate the main branch with ALL the production org metadata, rather than only the new changes introduced by working on work items.
Do I have this correct?
Hello @tsheiner ,
Yes, would be great to be able to populate metadata to the branch without having to use SFDX externally, but the big point with my suggestion comes with all suppported metadata, because I know we cannot deploy all metadata and settings through SFDX/Metadata API
I have implemented this feature as a Github Action which retrieves production metadata to Github nightly. I have chosen to retrieve the metadata to a "prod-read-only" branch, which has several advantages :
- it isolates a copy of production on a different branch, so we don't get confused when retrieving metadata which has just recently been promoted
- this schema can be extended to multi-org architectures where there are multiple production orgs being deployed from the same repo
- it can be used for pure production-org audits, independently of any delivery operations
@RupertBarrow could you share your github action ? It is interesting. Thanks
100% agree.! @RupertBarrow could you share it? Indeed needed in DevOps Center!
Hi @praulkar @lramosmtx , enjoy ! https://github.com/RupertBarrow/actions/tree/main/action-populate-repo-from-salesforce
This is definitely a big one for admins. For one thing, you can't roll back something if you don't have a prior version. The second thing is that most Admin don't have the tools do create their own, which means their master will only have things that have been deployed through DevOps Center.
