Most of the tests that currently cover core functionalities depend heavily on (and sometimes test) internal implementation characteristics. While they should be testing whether given implementation produces desired outcome (treating its implementation more as a black box).

_Current state of things is problematic for eventual internal improvements and refactors which occasionally we want to i

What would you like to be added:
Support for deploying vSphere storage Container Storage Interface (CSI).
It' GA already.

https://github.com/kubernetes-sigs/vsphere-csi-driver
https://cloud-provider-vsphere.sigs.k8s.io/

It requires vSphere 6.7u3+

Why is this needed:

• The in-tree cloud provider for vSphere is deprecated.
• The CSI is the standard way to implement the Storage

Describe the bug
When a user signs in using Auth.signIn() the "signIn" event is registered multiple times in the Hub listener

To Reproduce

1. Add a log inside the "signIn" event in the Hub.listener callback
2. Open devtools
3. Sign in using Auth.signIn()
4. Notice there is at least 4 or more logs and the same amount of network calls

Expected behavior
The sign in event shou

Description:

I'd like to be able to specify the IAM role Path on either a function or globals.

Observed result:

Able to specify Path on a Function or Globals

Expected result:

Path is set on the implicitly created IAM roles

This is a reminder for me or a task if anyone wants :P

Basically, The last two questions aren't really regex's questions.

To do:

• Move said questions to correct place.
• Add new regex questions (Python related!)?
• Maybe add a new ## Regex section, as it is a valuable skill

Support new Bucket Ownership Controls to ensure bucket owner owns all objects in the bucket

Use Case

https://docs.aws.amazon.com/AmazonS3/latest/user-guide/add-object-ownership.html

Ensure proper object ownership after cross account writes

Proposed Solution

cdk.Bucket to support passing ownershipControls to CfnBucket

Other

Coming from: aws ec2 describe-reserved-instances

I'm using disable_init to prevent terragrunt from accessing remote state bucket on its own (reason explained below). However, this also disables initializing the backend by terraform: it passes -backend=false to terraform init. As a result, the backend is not initialized and all terragrunt commands result in errors:

$ terragrunt plan
...
[terragrunt] [/tf] 2020/11/11 21:14:49 Running c