Several blueprints per yaml

Hi,

I have been searching the forum but can’t seem to be finding an answer to this question.
I am a little confused on how we are supposed to manage several blueprints within one single render file as there is no way to bind resources to a specific blueprint within the file.

I currently have a project Foo with a staging env and prod env. There are a bunch of self-hosted resources (Docker) that I intend to use on staging but not in prod.
If I define all my resources (prod and staging) in that single yaml file, then they all end up being part of the same Blueprint when synced in the UI.
My expectation would be to have a Blueprint that I can use for all my non prod environments in that project and another blueprint for the prod environment.
That seems to be a rather simple use case but I don’t understand how to achieve this with that single yaml file?

Thanks

Hi there,

Yes, this is one limitation of blueprints in their current format. You can’t define multiple environments (e.g., staging and prod) in a single blueprint unless they use exactly the same resources.

One option is to move one of the environment blueprints into its repo and have the blueprint services point back to the main repo, with the repo tag. There is a more detailed write of how to do this here: https://community.render.com/t/suggestions-how-to-have-a-permanent-staging/7280.

Regards,

Keith
Render Support, UTC+10 :australia:

Thanks @Keith for your reply.
This seems to be a rather common expectation, are there any plans to address this in the future?
Cheers,
S.

Hi there,

I can’t give specific timelines here, but yes, this is something we should address in the future.

Regards,

Keith
Render Support, UTC+10 :australia:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.