sayadi

# By default, the AWS EKS API creates the coredns deployment template with an annotation
# `eks.amazonaws.com/compute-type` equal to `ec2`. This prevents coredns pods from running on Fargate.
# Removing this annotation fixes the issue.
# More on: https://github.com/hashicorp/terraform-provider-aws/issues/11327
resource "null_resource" "edit_coredns" {
  provisioner "local-exec" {
    environment = {
      KUBECONFIG   = module.eks.kubeconfig_filename
      CLUSTER_NAME = local.cluster_name
    }

sayadi

@RestController
@RequestMapping("/properties")
public class PropertyController {

    private final Environment environment;

    @Autowired
    public PropertyController(
            Environment environment) {

sayadi

prop2=Production-specific value for prop2.

prop3=Production-specific value for prop3.

sayadi

spring.profiles.include=non-prod

prop3=Staging-specific value for prop3.

sayadi

spring.profiles.include=non-prod

prop3=Development-specific value for prop3.

sayadi

prop2=Non-production-specific value for prop2.

sayadi

prop1=This is a shared value across all profiles for prop1.

sayadi

spring.profiles.include=@spring.profile.from.maven@

sayadi

	<profiles>
		<profile>
			<id>default</id>
			<activation>
				<activeByDefault>true</activeByDefault>
			</activation>
			<properties>
				<spring.profile.from.maven/>
			</properties>
			<dependencies>

sayadi

version: 2
general:
  branches:
    only:
      - dev
      - staging
      - prod
jobs:
  build:
    docker: