adamant-dress-7332508/14/2019, 7:48 PM
but now the project name is not showing up on the dashboard. I made sure that the project name in Pulumi.yaml was set correct, any reason why
wouldn't name these correctly?
cool-egg-85208/14/2019, 8:05 PM
clever-sunset-7658508/14/2019, 9:07 PM
So if you do not have repository integration, I believe it will be empty like thatYes, I believe this is the case. cc @colossal-beach-47527 to keep me honest here.
colossal-beach-4752708/14/2019, 9:12 PM
, but will be available after you run
pulumi stack init
. (Since as part of the update, we look if you are running within a
repo, and if so, inspect the origin if it is a GitHub repo, etc.)
So it makes sense that the repo would be blank for a newly created stack.
The project name and stack name should be set when you run
. The project name is what is found in
pulumi stack init
, and is at the top of the “card with a white background”. The individual stack name is the label on each of those “purple rectangles” found on the project-card.
adamant-dress-7332508/14/2019, 9:59 PM
location for the repo? because for 1 of those shown, I've already run an update and it is located inside a git repo
colossal-beach-4752708/14/2019, 10:52 PM
does the tool lookup recursively fromYes, I believe that is the case. Depending on the specific repo is configured though, we may not be pulling your repository information. We only check for a remote namedlocation for the repo?
, and only then IFF the URI matches certain well-known forms. (i.e. we err on the side of only persisting data we can parse/extract rather than just including the raw remote URI.)
The specific code is here. If something seems amiss, and we should be pulling the repo information but are not, please file an issue and I can update the logic to detect your specific SCC provider, etc.
best-xylophone-8382408/15/2019, 9:24 AM
adamant-dress-7332508/15/2019, 4:06 PM
remotes on those. We are switching to github either way so no big deal just have to change our origin remotes there.
colossal-beach-4752708/15/2019, 5:25 PM
remote (change the domain/values if they are sensitive). Knowing the domain and/or URL structure, I can add support for those systems in Pulumi so things “just work” for you in the future.
As far as what you are missing out on, only two things come to mind.
- Like you called out at the beginning of this thread, we won’t be able to group your Pulumi Projects by their source repo when on your organization’s dashboard. That can be helpful to filter stacks, e.g. just hone in on the projects/stacks within your “website” or “data-tier” repository.
- On the “stack activity page”, we link to the repo commit that the update was deployed at in some cases. (Since e.g. for GitHub repos, if we know the branch, repo, and commit we can build the right URL to send you to.) So it’s possible we could do something similar and link to a private GitLab instance or Phabricator instance.
best-xylophone-8382408/15/2019, 5:29 PM
So it’s possible we could do something similar and link to a private GitLab instance or Phabricator instance.you can see gitlab URL structure on Gitlab itself it matches private Gitlab URLs, for instance
. You probably wont be able to reliably detect SCM , so if it was exposed somehow for us to set it can help
adamant-dress-7332508/15/2019, 5:41 PM
Repo Name > Project Name > Stack Name
and keep the repo icon around as a nice to have for common SCMs.
Project Name > Stack Name