We are trying to create an AWS amplify app. For CI/CD we want to integrate it with Github. I understand amplify has a way to add a Github account(personal with username and password), but I am not able to find a way to add a Github Enterprise account( that doesn't have such username and password credentials).
Is there a way to add Github enterprise to amplify, like how Codebuild allows to connect.
A GHE (GitHub Enterprise) server does support GitHub Actions
So check first if activating an action like amplify-cli-action or (depending on what you want to do) amplify-preview-actions would help in your case.
In term of credentials, those actions would need:
Navigate to AWS Identity and Access Management console
Under Users -> Add New User. Fill in the user name(GithubCI) and set Programmatic Access for Access type.
In permissions, select Create a new group, in a dropdown select Create policy.
In a policy creation menu, select JSON tab and fill it with a next policy statement, then hit review and save
Related
I have created a Azure Container Registry in my Azure subscription and wanted to use Azure Devops to build and push my containers. I am trying to create a service connection however when selecting my subscription the screen states "No registries found"
I also tried to create a pipeline using the Docker (Build and push an image to ACR) and this screen also cannot find my registry.
The registry exists and was created as a "Basic" SKU. I have tried other SKUs as well with no luck.
Any ideas of what I can do to be able to select my registry in Devops?
This could be caused by an expired token. Generally, we can try below ways to get it work (force refresh the token).
Go to Azure DevOps user profile page and switch to another directory, and then switch it back again. During the operation, it will force you to sign out and sign in again. Thus, it will refresh the token from AAD. If you have multiple directories here, then please do the same actions one by one, and then switch it back to the original directory (AAD) which you Azure DevOps organization needs to be backed to. After that try it again
Go to the affected ACR from Azure portal, then disable and re-enable admin account. (Click Update -> Enable/Disable the “Admin user” -> Save -> Disable/Enable the “Admin user” again -> Save). After that refresh the DevOps page and check if it works now.
I just created a new organization for my team on Azure DevOps. I wanted to activated the git access through username/password to begin with(for multiple reasons: We use Https, so no ssh certificate, and I've no idea how to use PAT with our current git client(sourcetree)).
Currently, when I go in my settings on "Alternate credentials", I get this:
But I've been into the organization page and I cannot find this settings? How can I enable it?
But I've been into the organization page and I cannot find this
settings? How can I enable it?
You can't enable that, the Alternate authentication credentials setting has been removed from Organization settings=>Policies for newly created organizations. Check the blog shared above in Michael's answer.
I've no idea how to use PAT with our current git client.
It's recommended to use PAT instead since you have no SSH certificate. Here're samples about how to use git+pat without pop-up window for credentials (Useful when you're running the commands in pipeline, since you can't enter credentials if there's pop-up window):
1.You can generate Git credentials to get temp username and password, and then use format:
git clone https://UserName:Password#dev.azure.com/OrgName/ProjectName/_git/RepoName
2.You can create a limited PAT(more secure then Full access) and use command:
git clone https://anything:{yourPAT}#dev.azure.com/OrgName/ProjectName/_git/RepoName
Same format when using git push...
Also you can clone the repo with git clone + URL from this button. Per my experience, it will prompt for credentials and save the credentials in local machine.
For Source Tree:
Url: https://OrganizationName.visualstudio.com
userName: The email address of your azure devops account
password: PAT
Enter correct URL format, click the refresh PAT button and enter the email as username, PAT as password. The authentication succeeds in my source tree for windows.
Looks like effective March 2, 2020 Alternate Credentials are no longer supported. Organizations created before then can use them for a short time to transition to PATs. New organizations do not have that option. Source
From Microsoft DevBlog:
Deprecation Timeline
Beginning December 9, 2019 we will disable and hide Alternate Credentials settings for organizations that don’t have Alternate Credentials set. This change will be in effect for all these organizations by December 20, 2019.
In the coming months we will work with our customers that are still using the feature, to help them switch to another, more secure authentication method.
March 2, 2020 – Start gradually disabling Alternate Credentials for all Azure DevOps organizations.
Legacy Organizations
If you have a legacy organization, the option would appear under Organization Settings, Policies (under the Security subheading). The toggle is called "Alternate authentication credentials"
I have registered an account with GitKraken and confirmed that I have rights to a repo on VSO. When I attempt to login, my uid and pwd and cleared from the text box and I can't login
Any guesses where the point of failure is? When I use Visual Studio, I can log into that TFS repo no problem
You can't use your VSO login directly in Git Kraken.
There are two ways you can approach this:
- Use a personal access token. In VSO, click on your profile icon -> Security - Personal access tokens. Create a new access token and use that as a password. Personal access tokens have an expiry date, so you will have to create a new one after some time.
use ssh. That is what I am using, as I think it is more convenient, but a bit more steps to set up. Here is a tutorial on how to set it up with VSO: https://learn.microsoft.com/de-de/vsts/repos/git/use-ssh-keys-to-authenticate?view=vsts
I am currently part of several organizations, which I have been previously invited to. I would like to create a new organization solely for myself. According to the documentation (https://www.ng.bluemix.net/docs/admin/index.html#orgmng) I should be able to go to 'Manage Organizations' and click 'Create an organization', but I do not have this option. How should I go about creating an organization?
For the public version of Bluemix Trial accounts can only create one organisation (which is created the first time you log in). If you add credit card details and move to a "PayGo" account then you are able to create multiple organisations.
On the dedicated or local deployments of Bluemix all admins are given the permissions to create their own organisations.
Only account owners with Pay-As-You-Go accounts can create an organization. You can create an organization by completing the following steps:
Using Bluemix Web GUI:
Click Account > Manage Organizations page.
Click Add a New Org.
Enter the org name.
Click Add.
Using Bluemix admin CLI
- cf ba create-organization <organization> <manager>
Where
<organization>: The name or GUID of the Bluemix org to add.
<manager>: The user name of the manager for the org.
My team is using Github for code hosting and Unfuddle for ticketing. Is it possible to connect Github to Unfuddle so that we are able to update/close tickets from our commit messages?
As markdorison notes, there are service hooks in github enterprise to do this.
First, you need to make sure your github account has the permissions necessary to administer your repo. You need to be set up as a repository "owner."
Once you have those permissions, if you go to the overview page of your github hosted repository /ORGANIZATION/REPOSITORY, you will see a row of familiar tabs, with one new member at the far right:
Code Network Pull Requests Issues Graphs Admin
Click on admin, and you'll see a menu at the left of the admin page with a link to "Service Hooks."
Once you're on this page, scroll (far) down to find the "unfuddle" service hook.
Click on the Unfuddle service hook and a small form will open up in the upper right of your browser. Fill it out like so:
Subdomain: Your organization's unfuddle subdomain, ie ORG.unfuddle.com
Repo Id: The numeric Id of the github repository you are trying to connect to unfuddle.
Username: Your unfuddle user account name.
Password: Your unfuddle user account password.
_ HttpOnly (check if appropriate)
√ Active (set to active to use this service, uncheck to stop using it)
Then click the "update settings" submit button.
On completion, you will see a new button called "Test Hook." Click that to test the connection and make sure it is working.
Within a few minutes, you should start seeing commit history being reflected in Unfuddle's repository listings.
Pro Tip: Set up an Unfuddle account just for external services like github, and use this account instead of individual users accounts, for creating the service hookup.
This functionality is provided from the Unfuddle service hook offered in Github. You can find it in the admin section of your repository.