This topic explains how to use the ACM API with sample code.
Get the SDK
Enter the following POM configuration to establish API dependency on the SDK.
<dependency>
<groupId>com.alibaba.edas.acm</groupId>
<artifactId>acm-sdk</artifactId>
<version>1.0.8</version>
</dependency>
<! -- Remove the following if logging implementation is available. -->
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
<version>1.1.7</version>
</dependency>Code example
import java.util.Properties;
import com.alibaba.edas.acm.ConfigService;
import com.alibaba.edas.acm.exception.ConfigException;
import com.alibaba.edas.acm.listener.ConfigChangeListener;
import com.alibaba.edas.acm.listener.PropertiesListener;
// Sample code, for sample test only.
public class ACMTest {
// Attribute/Switch
private static String config = "DefaultValue";
private static Properties acmProperties = new Properties();
public static void main(String[] args) {
try {
// Copy the corresponding values from the namespaces page in the console.
Properties properties = new Properties();
properties.put("endpoint", "$endpoint");
properties.put("namespace", "$namespace");
// Access ACM with instance RAM role
// properties.put("ramRoleName", "$ramRoleName");
properties.put("accessKey", "$accessKey");
properties.put("secretKey", "$secretKey");
// If it is an encrypted configuration, then add the following two lines for automatic decryption.
//properties.put("openKMSFilter", true);
//properties.put("regionId", "$regionId");
ConfigService.init(properties);
// Actively get the configuration.
String content = ConfigService.getConfig("${dataId}", "${group}", 6000);
System.out.println(content);
// Add listeners to the configuration during initialization, which calls back a notification when the configuration is changed.
ConfigService.addListener("${dataId}", "${group}", new ConfigChangeListener() {
public void receiveConfigInfo(String configInfo) {
// After the configuration is updated, the latest value is returned to the user via this callback function.
// Remember not to make blocking operations in callback function. Otherwise the notification thread will be blocked.
config = configInfo;
System.out.println(configInfo);
}
});
/**
* The following listener can be used if the content of the configuration value is in properties (key=value) format. This allows you to manage multiple configuration items in one configuration.
*/
/**
ConfigService.addListener("${dataId}", "${group}", new PropertiesListener() {
@Override
public void innerReceive(Properties properties) {
// TODO Auto-generated method stub
acmProperties = properties;
System.out.println(properties);
}
});
**/
} catch (ConfigException e) {
e.printStackTrace();
}
// Keep the main thread alive throughout the test, because the configuration subscription runs in a daemon thread, which exits once the main thread exits. The following code is not required in a real environment.
while (true) {
try {
Thread.sleep(1000);
} catch (InterruptedException e) {
e.printStackTrace();
}
}
}
// Expose the configuration value via the get configuration API for external use.
public static String getConfig() {
return config;
}
// Expose the configuration value via the get configuration API for external use.
public static Object getPorpertiesValue(String key) {
if (acmProperties ! = null) {
return acmProperties.get(key);
}
return null;
}
}Options of passing parameters
To help you get onboard, the sample code initializes the parameters with code. However, the real production process may involve different environments (namely different accounts, regions, or namespaces), and the parameters vary with environments, so you must use variables to pass the parameters. To facilitate the input parameter configuration and reduce the configuration cost, ACM provides multiple options of passing parameters.
Note EDAS automatically injects for you during the publishing, and therefore you don’t
need to take any action.
| Initialization parameters | How to pass parameters |
|---|---|
| endpoint | From highest priority to lowest priority:
|
| namespace | From highest priority to lowest priority:
|
| ramRoleName | Note: The authorization priority is higher than the accesskey/ridgekey priority from
high to low
|
| accessKey/secretKey | From highest priority to lowest priority:
|