Cloudformation-coverage-roadmap: AWS::Athena::Workgroup -WorkGroupConfiguration/WorkGroupConfigurationUpdates should support setting engine version

Created on 15 Dec 2020  Â·  2Comments  Â·  Source: aws-cloudformation/cloudformation-coverage-roadmap

1. Title

AWS::Athena::Workgroup-WorkGroupConfiguration/WorkGroupConfigurationUpdates

2. Scope of request

AWS::Athena::Workgroup -WorkGroupConfiguration/WorkGroupConfigurationUpdates should support setting the version of the Athena engine

3. Expected behavior

It should allow you to select the following:
- Default => let AWS decide/upgrade
- 1 => Manually set Version 1
- 2 => Manually set Version 2

4. Suggest specific test cases

5. Helpful Links to speed up research and evaluation

Athena docs: https://docs.aws.amazon.com/athena/latest/ug/engine-versions-changing.html#engine-versions-changing-changing-the-engine-version

6. Category (required)

Analytics

7. Any additional context (optional)

Most helpful comment

At the time this issue was opened, there wasn’t any support for updating/setting the version. However, now it seems to work, and the documentation has also been updated. I have, however, not seen anything about it in the release notes so I’m not sure if this is yet “official”.

As an aside, I do find it very odd (and very contrary to normal CF functionality) that you have to use a completely different attribute (WorkGroupConfigurationUpdates vs WorkGroupConfiguration) to update an existing resource vs when you create it.

All 2 comments

Did you try to set the SelectedEngineVersion to Athena engine version 2 with EnforceWorkGroupConfiguration enabled ?

...
WorkGroupConfiguration:
  EnforceWorkGroupConfiguration: true
  EngineVersion:
    SelectedEngineVersion: Athena engine version 2
...

At the time this issue was opened, there wasn’t any support for updating/setting the version. However, now it seems to work, and the documentation has also been updated. I have, however, not seen anything about it in the release notes so I’m not sure if this is yet “official”.

As an aside, I do find it very odd (and very contrary to normal CF functionality) that you have to use a completely different attribute (WorkGroupConfigurationUpdates vs WorkGroupConfiguration) to update an existing resource vs when you create it.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

JohnPreston picture JohnPreston  Â·  3Comments

rjpereira picture rjpereira  Â·  4Comments

msaggar picture msaggar  Â·  3Comments

san-san picture san-san  Â·  3Comments

mildebrandt picture mildebrandt  Â·  3Comments