Issue #, if available:
In python sdk, customers can specify the spark container with either image_uri or framework_version. With just framework_version, an default tag of the image will be used(e.g, 2.4-cpu). Currently all integration tests are using image_uri directly, need an integration test to test default tag.
Description of changes:
Add integration test for default tag by just specifying framework_version.
Create a new target because this new integration test will only be running for prod stages. The reason being that Sagemaker python sdk is responsible for building the default tag by maintaining a json file that has a map between only regions and prod accounts.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issue #, if available: In python sdk, customers can specify the spark container with either image_uri or framework_version. With just framework_version, an default tag of the image will be used(e.g, 2.4-cpu). Currently all integration tests are using image_uri directly, need an integration test to test default tag.
Description of changes: Add integration test for default tag by just specifying framework_version.
Create a new target because this new integration test will only be running for prod stages. The reason being that Sagemaker python sdk is responsible for building the default tag by maintaining a json file that has a map between only regions and prod accounts.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.