Nick

Had the same problem Found commit 76225528b3903fc9eafcb8163c7ebfdf34237e8b works, my config: ``` location /grid/ { gridfs assets; mongo 172.16.1.154; } ``` I notice at this stage it can't however resolve using...

Sorry for not fixing your problems =) It's something that works for me, at least. If I were you, I would check out that commit, recompile, and see if it...

I would've thought this would be very important feature for the agent; would think one of the most common use cases is someone spinning up an ec2 instance (now AL3...

Unfortunately I think this isn't currently suppored via API https://learn.microsoft.com/en-us/rest/api/azure/devops/

I notice the CI failure isn't related to that code :/

This is because `--ignore-bad-template` is supplied to `cfn-lint` https://github.com/aws-cloudformation/cfn-lint-atom/blob/60f95f6a74c989c19e8fbe46cd884efaf71ef1df/lib/atom-cfn-lint.js#L168 @kddejong would you be OK with us removing this? Can make PR

@asyschikov did you find out? Looks like AWS SSO supports only getting creds interactively via console? https://aws.amazon.com/blogs/security/aws-single-sign-on-now-enables-command-line-interface-access-for-aws-accounts-using-corporate-credentials/

I have a simple replication here ```terraform terraform { required_providers { fortimanager = { source = "fortinetdev/fortimanager" version = "1.12.1" } } } provider "fortimanager" { hostname = "x.x.x.x" username...

btw I found this issue isn't present in version `1.8.0`