Often wondered, how do you force ECS fargate to redeploy with your CI/CD pipeline when nothing changed in the terraform script other than the code rebuild into docker image with the same tag?

You certainly don’t want to see this in your CI/CD pipeline with terraform apply:

Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Terraform AWS provider has this attribute force_new_deployment under aws_ecs_service, which if set to true should force redeploy with terraform apply.

resource "aws_ecs_service" "main" {
name = "my-app-service"
cluster = aws_ecs_cluster.main.id
task_definition = aws_ecs_task_definition.app.arn
desired_count = 2
launch_type = "FARGATE"
force_new_deployment = true

That attribute…

Spring cloud OpenFeign supports three underlying implementations for feign client:

  • Default
  • ApacheHttpClient
  • OkHttpClient

You often come across use cases, where the feign client should use an HTTP proxy to make the outbound API call.

Depending on what implementation is used in your project, here is how you configure the feign client to use HTTP proxy:

TRICK: You configure the feign client and then override the default client bean in the Spring application context.


Comes out of box client with spring cloud, no additional config or dependency is needed:

import feign.Client;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import java.net.InetSocketAddress;
import java.net.Proxy;
public class FeignConfiguration {
public Client feignClient() {
return new Client.Proxied(null, null,
new Proxy(Proxy.Type.HTTP, …

Are you challenged with showing a custom 404 error page built in React when your app routing is handled using HashRouter instead of BrowserRouter and you are using spring boot to deploy your app as static SPA?

Then, you are on the right blog looking for the right solution.

First Thought: Why not just use BrowserRouter then?

Not always the available options right? Especially when we prefer:

  • Backward compatibility (supporting older browsers)
  • Separate server-side & client-side routing

First Instinct: Shouldn’t it be simple? Both React & Spring has routing options?

Let’s understand more in detail the problem statement with some…


If you are working for an enterprise solution, where you customize app theming per end client or you are a creative app developer who loves keeping users enticed with new themes, then you understand how important it is to support the Dynamic Theming of the app.

Theme configurability may include some or all of these, but not limited to:
App Branding, Background image, Watermark, Color scheme, Logo, Font, etc

We don’t want to bundle the app styling inside the installer packaging, so be able to configure it from the server on the fly. This not only gives you an easy…

Problem Statement

Ionic natively doesn’t provide any graceful input component for capturing user input for currency or decimal data (with defined precision and separator).

With native <ion-input>, capturing user input in decimal format can get ugly, prone to validation errors, and of course not a great user experience.

<ion-input placeholder="$0.00" inputmode="decimal" [(ngModel)]="entry" name="amount"></ion-input>

Amith Kumar

Lead Full Stack & DevOps Engineer

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store