externalized | handy DSL that makes it easier to work | Reflection library

1. The modern way of doing this is by decoupling your policy and code - i.e. having a seperate microservice for Authorization - here's a part in a talk I gave at OWASP DevSlop about it. You'd want you code in the middleware to be as simple as possible - basically just querying the Authorization microservice. That service basically becomes your PDP (in XACML terms).  This is true for both monolith and microservices (the assumption is you'll end up having more microservices next to your monolith anyhow). 
   To implement the Authorization microservice / PDP you can use something like OPA (OpenPolicyAgent.org) and then use OPAL as a PAP and manager for PIPs.

2. The query to the PDP should include what the user is doing (but not what the rules are). You can do this based on the Route (common when doing service-mesh), but often it's better to define a resource/action layout which becomes part of the query and is independent directly of the application route. Take a look at the Permit.io Policy-Editor which does exactly that kind of mapping. (Permit also uses both OPA and OPAL internally)

3. Very good point. You don't want your PDP to constantly be querying other sources per incoming query to it (though its okay if you do it for a few edge cases) - What you want is to load data gradually in the background in an asynchronous fashion. Ideally in an event-driven fashion (i.e. have events propagate in realtime from the data sources into the PDP). This is exactly what you can do with OPAL.

Ok, found the problem is because of the current AXIOS is not support for esm. Thus when run after build, Axios is not a constructor show up.

But i found the the redaxios is supported to build for that. Just dont have the interceptor, and the interceptor didnt merge in. I self create fork and update based on the previous commit. Tested on my side thats working.

https://github.com/developit/redaxios/pull/75

If you guys could, help me to review and see where to improve. Thanks.

I tried on a fresh jenkins and it works as expected. If plugin(java class) is able to read environment variables and jenkins inject environment variables, everything should work.

I think your error is the environment variable syntax. Accoding to this you should use ${env.VARIABLE_NAME} to use environment variables in a pom.xml. So in your case, your pom.xml should be like this:

https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html#including-declarations-in-your-npm-package

Have you tried adding the "types" property? I can see your dist folder contains the main.d.ts file so it should be a matter of just making it be recognized (by adding that property)

Please go through the 12-factors of microservices.

The question to your answer in simple words is, Every microservices is having its isolated database( maybe the dedicated table or in NOSQL it's separate bucket for that microservice). And most important, only that microservice can interact with its databases: all other services must go through that service (e.g. via REST/HTTP or a message bus).

Read this link which gives a detailed explanation.

https://12factor.net/backing-services

See below URL::

https://www.nginx.com/blog/microservices-reference-architecture-nginx-twelve-factor-app/

Since you're passing an empty dependencies array, the effect only gets run once. You can add props.name to the dependencies array to make sure fetchData gets called when props.name changes.

Try the following

root@foobar:~/# java -jar ~/foo.jar --spring.config.name=sheets.properties

By default Spring Boot will override your configuration files based on the location they are placed. By default however it will try to load as property file a file with name application.properties or application.yml. Because you have a custom properties file you have to declare it.

As for file location. Outer configuration files override the inner files. So if you have in your resources inside jar a sheets.properties the outer file in your current directory will override it. You don't need any special property for that.

Hence if you execute your Jar with the above command your properties file from your current directory will be loaded.

Check the following link to understand how to apply externalized configuration and also from which directories spring boot tries to load properties by default.

Spring boot externalized properties

We can leverage the fact that we can pass tuples as a MultiIndex slicer. Also we slightly adjust your my_dict. Then we apply a simple for loop:

Try this: