Support for external_id and session_name in s3 backend assume_role

[bjornrog]

We need support for external_id in the s3 backend, so we can use the same credentials as for the aws provider.

I have looked at the code and it seems to be a very simple fix, as the AWS auth mechanism used by the backend is the same as for the aws provider.

I have written a working version, but was not able to branch (ERROR: Permission to hashicorp/terraform.git denied to ...).

[tombuildsstuff]

Update: looks like @stack72 has already submitted a Pull Request to cover this 😄 (this didn't appear until I'd refreshed the page!)

---

Hi @bjornrog

Thanks for both reporting and taking a look into this :)

I have written a working version, but was not able to branch (ERROR: Permission to hashicorp/terraform.git denied to ...).

We're using Forks to allow contributors to propose changes to Terraform via Pull Requests - which means that (most) contributors don't have direct push access to this repository (which is the error you're seeing here).

It appears that you haven't created a Fork yet, so there's some more information available here - but essentially you can create a Fork by pressing the "fork" button in the top right of this page. Once the fork exists, you can add it to your local Terraform clone by using the following commands:

git remote add bjornrog git@github.com:bjornrog/terraform.git

At this point you should be able to push the changes to your Fork via:

git push bjornrog <branchname>

Once that's done - you can then open a Pull Request :)

Thanks!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.