We are trying to deploy an app, but the github account link doesn’t work properly (at least not in a team/multi user environment).
The first user is able to link/install DigitalOcean into the organization (with all repository access), and is able to see the repositories when creating new components.
When a second user (from the same team and github organization tries to create a component, DO doesn’t seem to understand that the app already contains a link) - it asks to link the github account again, and since it`s already installed it gets redirected to the github settings page instead of showing the repository list.
It seems that the link is getting stored in a per-user basis?
Is it a bug or am I doing something wrong?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
I was being stupid. Turns out you need to have DigitalOcean installed in BOTH the organization and your own user. Trying to solve some permission stuff before I removed DigitalOcean from my GitHub user.
Hey all,
Just answering an old question in case someone else stumbled upon it.
The issoue could be comming from the fact that when you originally granted App Platform access to Github you only gave it limited permissions. To run through the Github auth process again you can visit https://cloud.digitalocean.com/apps/github/install
If you have multiple orgs associated with your Github account, be sure to choose the org that your private repo is in.
Then on the Repository Access screen, either choose “All Repositories” or specifically select the now-private repo you want to deploy.