Get functional tests working against Dremio Cloud #47
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Made changes to the tests to refer to the S3 bucket instead of the GCS bucket. The source name is still the same, but the root_path in the tests will now prefix the bucket name, instead of the source name. In addition, I've added a dremio cloud profile and dremio software profile to run the functional tests against. Since the privileges table is different in Dremio Software and Dremio Cloud, the grants macro needs to check which profile we're using in order to get data from the privileges table.
Description
Grants Macro
Functional Tests Configuration
--profile
These changes allow us to specify 'dremio_cloud' or 'dremio_software' as the profile when running the functional tests
Datalake Constant
Related Issue
Additional Reviewers
@jlarue26
@ArgusLi